home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC Graphics Unleashed
/
PC Graphics Unleashed.iso
/
ch01
/
new_faq
< prev
next >
Wrap
Text File
|
1994-07-29
|
9KB
|
245 lines
--------------------------------------------------------------------------------
PART I -- TIPS FOR DIFFERENT OPERATING SYSTEMS
--------------------------------------------------------------------------------
(1). WINDOWS (from Oliver Weyand)
Start Display under WINDOWS through a PIF file. Give display all
memory you have (parameters -1 for ems and/or xms in pif-editor),
because you will have no swap-space in a windows-shell (that's
ok, because windows will manage the virtual memory). Make sure
NOT to use a graphic driver in protected mode (windows will show
you one of this boring error messages), so don't add the 'driver ::p'
statement to your go32 environment.
With DISPLAY 1.82 or latter, you are not forced to use VESA driver.
(2). OS/2 (from Oliver Weyand, chbrin3@nyx.uni-konstanz.de)
Load a vesa-driver in your autoexec.bat (under OS/2 this file is only
executed when you open a DOS shell). Don't use 'driver ::p'. Give it
enough memory: the standard 4MB dpmi-memory are not enough. Open the
menu for the DOS shell and edit the entries for memory (EMS,XMS,DPMI).
Also edit the entries for graphic capabilities. If you won't use the
autoexec.bat file for display's DOS session, enter the name of the used
batch file. If you don't understand this things refer to your OS/2
manual. For further hints how to setting up DOS shells under OS/2 refer
to the hints that can be found on many ftp servers (if you are an OS/2
user you will know them, i.e. hobbes).
It was reported to me, that display won't run under OS/2 at all. Sorry
guys, can't help you. I just tell you what has worked for me with version
2.1 on my 486/33. BTW, if you search a good viewer-converter for OS/2
give Joe-View a chance (joevw128 or higher, shareware).
(3). Novell DOS 7 (from Oliver Weyand, chbrin3@nyx.uni-konstanz.de)
When running display under NWDOS 7 there is only one thing that is
different from MSDOS: the multitasking environment. You have to make
sure, that display can't use dpmi. So you can either type 'dpmi off'
at the NWDOS prompt or add the nodpmi statement to the go32 variable
(set go32=nodpmi ...) in the runme.bat. Because the NWDOS multitasker
supports only standart VGA mode you should use display not in graphics-
text mode (if you do display will switch to plain text after an error
message). Further the only available graphics mode is 320x200-8bit.
You can convert files or generate movies in the backround, while you
play a your favourite game (beware, that you need at least a 486 with
at least 8-16MB RAM). Because I use NWDOS on a stand-alone machine I
can't say anything about using display with Netware-Lite.
(4). LINUX
If someone knows anything about the dos-shell of linux please fill in
here. Because there are other good graphic programs running under X11
I'm not sure if there is need to run display under linux. But anyway, if
someone has done it please write, post, e-mail.
--------------------------------------------------------------------------------
PART II -- OTHER FAQS
--------------------------------------------------------------------------------
Q: How can I convert group of 24-bit images to 8-bit images with the same
palette table ?
A: Use the following steps:
1. Find a palette table:
Tag the images you want. Select 'accumulation quantization' to
produce a palette table.
- or -
press F5, then 'load a palette table'.
2. press F4, then change 'number of colors option' to 'no effect'.
3. press F5, then select 'push palette table'.
4. Tag the image you want. Select 'batch conversion' with two special
effects:
(1) 'pop palette table'
(2) 'color quantization' with 'current palette' option.
Q: How can I view the original palette table of an image ?
A: press F4, then change 'number of colors option' to 'no effect'.
Q: How can I resize image using percentage ?
A: Just add '%' to end of number, like '120%'.
Q: Why does this program show the message, 'CPU must be in real mode' ?
A: It is likely that you have 'device=emm386.exe noems' in config.sys.
Remove 'noems'.
Q: What is 'response file' ?
A: Response file is used to overcome the 128-byte limit in command line
length. You can put anything in response file just as in command line.
For example, you can put the following lines in IMAGE.LST :
aaa.gif
bbb.jpg
ccc.bmp
then use 'DISPlAY --slide @IMAGE.LST' to do slide show.
Q: What is 'description file' ?
A: Desciprtion file is a file containing the description for each image
in current directory. It can help you remember what is in each image.
You can change the file name to whatever you want (Please read the
TEXT section in config.dis).
Please see PART III for the format.
Q: What files are needed for minimal usage ?
A: The minimal set of needed files is :
GO32.EXE, DISPLAY.EXE, RUNME.BAT, one Video Driver, CONFIG.DIS,
EMU387(if you don't have x87), Fonts(if you want contact sheet).
Any thing else can be deleted.
--------------------------------------------------------------------------------
PART III -- SOME FILE FORMATS
--------------------------------------------------------------------------------
Palette File Format
-------------------
offset length content
0 8 "DISPpal0"
8 4 number of colors(Intel order).
12 4 R,G,B,A for each color.
... ... ......
YUV Format (from Berkeley MPEG ENCODER package)
----------
The U and V components are subsampled 4:1.
To give you an idea of what format the YUV file must be in, the following
code will read in a YUV file:
unsigned char **y_data, **cr_data, **cb_data;
void ReadYUV(char *fileName, int width, int height)
{
FILE *fpointer;
register int y;
/* should allocate memory for y_data, cr_data, cb_data here */
fpointer = fopen(fileName, "r");
for (y = 0; y < height; y++) /* Y */
fread(y_data[y], 1, width, fpointer);
for (y = 0; y < height / 2; y++) /* U */
fread(cb_data[y], 1, width / 2, fpointer);
for (y = 0; y < height / 2; y++) /* V */
fread(cr_data[y], 1, width / 2, fpointer);
fclose(fpointer);
}
Raw RGB Format
--------------
for (y = 0; y < height; ++y)
for (x = 0; x < width; ++x) {
read RED; /* 1 byte */
read GREEN; /* 1 byte */
read BLUE; /* 1 byte */
}
Raw GREY Format
---------------
for (y = 0; y < height; ++y)
for (x = 0; x < width; ++x)
read GREY; /* 1 byte */
Contact Sheet Script File Format
--------------------------------
1. Lines start with # are comment lines.
2. You must add this string to start of the file : "contact_sheet". This
string is an ID of script file.
3. You can write up to 2 strings for each image file in script file.
Each string can be up to 49 characters.
Strings are separated with the character '|'.
For example : I am 1| You are 2
4. If possible DISPLAY writes the two strings in the same line.
For example: I am 1 You are 2
^ Strings are separated with one SPACE character.
If the total length of two strings is too long, DISPLAY writes the two
strings in two lines.
For example: I am 1
You are 2
5. The following is a sample script file:
--------Start--------
# This is a sample file
contact_sheet
KIKI-TON.GIF Kiki's| gif file
N.GIF Nausicaa| gif file
NAUSICAA.GIF Another Nausicaa
PORCO.GIF Porco Rosso
TOTOROS.GIF Totoros| gif
WOTW1.GIF |line 2 only
--------Stop--------
Description File Format
-----------------------
Format:
<filename.ext> <Any string up to 99 characters>
For example:
aaa.gif this is aaa.gif
bbb.jpg I am bbb :-)
cat.bmp Oh! There is a cat in this image.
Batch Contact Sheet Script File Format
--------------------------------------
1. Lines start with # are comment lines.
2. You must add this string to start of the file : "batch_contact_sheet".
This string is an ID of script file.
3. This file is for command-line use only.
4. The format of user input string is in 'Contact Sheet Script File Format'.
5. SHEET.TPL is a documentation file. Read it.